2.16.3 Figure 138: Service Initialization.This section comprises the subsections Description, Used AT Commands, Flow Chart, Hints and Examples. To move to these subsections please use the Navigation Frame or the appropriate buttons on the toolbar.
2.16.3.1 This chapter describes basic settings recommended to configure the internet services: FTP, SMTP, POP3, Socket and HTTP.
• It is allowed to configure maximum 3 HTTP, 6 Sockets (The sum of Listener Sockets and Client Sockets is 6 and the number of Listener Sockets are limited by 2), 1 FTP, 1 POP3, 1 SMTP profiles within those 10 connection profiles.
• The services can be configured to use any of the connections which have been configured during the connection initialization by setting the <conId> parameter accordingly.
• It is possible for every service to setup the retransmission mechanism. The parameter like <tcpMR> and <tcpOT> can be set or the values specified with AT^SCFG will be used. Additionally is it possible to set the <tcpIRT> parameter, but only with the AT^SCFG command.
- The <tcpOT> parameter specifies number of seconds to wait before closing a conection if TCP/IP packets are not acknowledged.
- The <tcpIRT> parameter determines the time (in seconds) the TCP/IP stack will wait before starting the first retransmission of packets during the initial connection establishment phase.Figure 139: The Retransmission mechanism.
2.16.3.2
2.16.3.3
2.16.3.3.1
• The following examples describe the configuration of the FTP GET and PUT service. FTP GET enables download of data and FTP PUT upload.Figure 140: FTP GET InitializationFigure 141: FTP PUT Initialization
2.16.3.3.2 Figure 142: SMTP Initialization.
2.16.3.3.3
• The following example describes the settings required to retrieve the chosen email specified by the <pNumber> parameter.Figure 143: POP3 Initialization.
2.16.3.3.4
• In this example the socket client UDP to the echo port (7) of the given server has been configured. Echo port belongs to the well known ports.Figure 144: Socket Client UDP Initialization.Figure 145: Socket Listener TCP Initialization.
• Figure 146: Socket Client TCP Initialization.
2.16.3.3.5 Figure 147: HTTP Initialization.
2.16.3.4
• Note that some terminals e.g. ZOC support the ASCII character set but some modules use the GSM character set per default. The problem is, that some special characters e.g. ‘@’ are coded differently in those character sets. It is advisible to set the <alphabet> parameter to 1.
• The FTP PUT example shows how to upload the text file. In order to upload a binary file, the type of the <address> parameter should be set to “i”.
• If the <user> and <passwd> parameter shall be used for SMTP authentication, it is important to set <smAuth> to 1.
• If the website requires <passwd> and <user> in HTTP GET example, both parameters should be set and the
<hcAuth> parameter should be set to 1.
• In the Socket example it is important to set the port number of the chosen server, which is really defined and
not protected by e.g. firewall.
2.16.3.5
2.16.3.5.1
2.16.3.5.2
2.16.3.5.3
2.16.3.5.4
2.16.3.5.5
|